Determine the Scope

The first step is determining the scope of the migration.

• Which datasets (localizations) did you use in V8i?
• Did you create your own datasets?
• Did you add and modify and, possibly, remove files throughout the dataset or did you customize for specific product features?
• Did you modify common files in WorkSpace\ProStructures\--files outside the Localised and output folders?
• Did you create ProStructures projects?
• Which Rebar detailing projects did you use-USA_Canada, Metric, other?
• Did you create your own Rebar detailing projects?

The number of dataset/detailing project combinations you worked with determines how many ProStructures-extended workspaces should be created in the CONNECT Edition.

Create the Base WorkSpaces

If you created the dataset or extensively customized a delivered dataset, do the following to create the base workspace:

1. In configurationInstallationFolder\Configuration\WorkSpaces\, copy WorkSpaces\Template\WorkSpace.Template to newName.cfg.
2. Also in the WorkSpaces folder, create a subfolder named newName.
3. Duplicate the folder structure of WorkSpaces\anyExistingName\Standards\ in WorkSpaces\newName\Standards\. Do not copy the files.
4. Create an empty text file named application.cfg in WorkSpaces\newName\Standards\ProStructures\.
5. Create an empty WorkSets subfolder in the newName folder.

Otherwise, follow the instructions in Creating a New WorkSpace . Use the name of the delivered CONNECT Edition workspace that matches the V8i dataset for existingName

Customize the WorkSpaces

If the base workspace is not a copy of a delivered CONNECT Edition workspace, all files from V8i must be migrated; otherwise, work with just the added and modified and, possibly, removed files in V8i.

• See ProStructures Dataset Migration for details on migrating ProStructures dataset files.
• See WorkSpace\Rebar Migration for details on migrating Rebar detailing projects.
• See WorkSpace\ProStructures Migration for details on migrating the files outside the Localised and output folders. Note that while most V8i files were moved to the product directory, some files were moved to the workspaces.

Add configuration variables to workSpaceName\Standards\ProStructures\application.cfg when the customized workspace files replace or supplement common data files.

Migrating ProStructures Projects

If you created and worked with ProStructures projects, see ProStructures Project Migration for information on migrating the projects to ProStructures-extended worksets.

Migrating V8i Configuration Variables

A short list of configuration variables was supported in V8i. See Appendix B - SS8 Configuration Variable Migration for the list and information on their status in the CONNECT Edition.

The exact migration of the ProStructures application variables and the files that they found should be based on why the variables were set:

• If the variable was used to relocate a tree of data file folders, migrate the files to a ProStructures-enabled workspace using the general procedure in Migrating Customizations from V8i.
• If the variable was used to relocate a data file folder, move the files to an appropriate folder in a ProStructures-enabled workspace and, if necessary, add the configuration variable to workSpaceName\Standards\ProStructures\application.cfg.
• If the variable was used to relocate an output folder and the location is still appropriate for a workset, add the configuration variable to workSetName\Standards\ProStructures\application.cfg.
• If the variable was used to override a default file name or folder location, move the file to a ProStructures-enabled workspace and, if necessary, add the configuration variable to workSpaceName\Standards\ProStructures\application.cfg.